Fix some memory leaks #20
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If a map has a name it won't be freed uio_free_info causing a memory leak.
To prevent memory leaks uio_free_info is needed by the user of the library
When a uio_info_t doesn't match the searched name if will be freed
This was referenced Sep 2, 2021
VirtualLG
approved these changes
Jan 13, 2022
VirtualLG
approved these changes
Jan 13, 2022
VirtualLG
approved these changes
Jan 13, 2022
|
I used the above changes but still got a leak. @modbw |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are some memory leaks in libuio which I try to fix. Memory leaks where detected by valgrind. After these changes my test cases don't report any memory leaks.